feat: add agentic-harness plugin (harness-setup + harness-review)#8
Merged
Conversation
…e archive path, schema row)
On explicit request, harness-setup can dispatch a search-optimized subagent to find candidate MCP servers and plugins that fit the project, check the local config for already-available tools, and — only with explicit per-tool approval — register accepted tools by role in a tools.md registry under the orchestrator (role, preferred tool, alternative, status). Agents and skills reference tools by role and fall back to the alternative when one is unavailable. Periodic tool review is documented in maintenance.md (assess via harness-review, act via setup).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
agentic-harness, an MIT plugin for themrbogomipsmarketplace that stands up, assesses, and maintains a project-local agentic harness — the agents, skills, and orchestrator under.claude/that make a repo work well with Claude Code. It is a meta-tool: it builds and maintains the agents/skills that do the domain work, rather than doing that work itself.Independent, clean-room reimplementation inspired by the open-source
harnessplugin by revfactory (Apache-2.0); all prose re-authored, anonymized, and in the marketplace house voice. Credit is in the repo README only.Architecture — two skills on a read/write axis
harness-setup(writer): domain analysis → execution-mode + architecture-pattern selection → generate agent definitions → create skills → build orchestrator → register theCLAUDE.mdpointer → record change-history → capture feedback. Also extends, applies a review context, and syncs drift.harness-review(read-only): inventories.claude/, reads theCLAUDE.mdpointer + change-history, detects drift, and assesses effective usage from a fixed signal set (project auto-memory, the pointer + history, the.claude/inventory, the tools registry), then emits a prioritized review context that hands off toharness-setup.The loop is review → setup → review again — one reader, one writer.
Three cross-cutting concept docs live once in
agentic-harness/shared/(harness-model,claude-md-pointer,execution-modes) and are cited via${CLAUDE_PLUGIN_ROOT}/shared/...; per-skill references live under each skill'sreferences/.Notable design points
harness-setupStep 1b, on request only): a search-optimized subagent finds candidate MCP servers and plugins fitting the project's domain/stack and checks the local config. Nothing is adopted without explicit per-tool approval. Accepted tools are registered by role in atools.mdunder the orchestrator (role → preferred tool → alternative → status); agents and skills reference tools by role and fall back to the alternative when one is unavailable. Periodic tool review: assessed byharness-review, acted on byharness-setup./agentic-harness:harness-setupand/agentic-harness:harness-review.agentic-harnessinserted first inmarketplace.json(alphabetical).Test plan
bash tests/ci/run-structural-tests.sh→ "All test suites passed" (plugin, references, connectors)~~tokens, noCONNECTORS.mdrequireddescription:lines; both SKILL.md bodies < 500 lines (221 / 134)references/resolve; all shared docs cited via${CLAUDE_PLUGIN_ROOT}/shared/...harness-setupshould NOT trigger on assess/audit/usage phrasings (those go toharness-review);harness-reviewshould NOT trigger on build/extend/register/sync/fix phrasings (those go toharness-setup). The one subtle boundary — "is there a better tool?" (assess → review) vs "swap the tool" (act → setup) — is handled by the trigger verb.